default_app_config is no longer needed #71
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
Thanks for the PR. I appreciate that Django 1.x and py 2.7 are now way out of support and anyone running systems in production should probably be using something much more up to date. At the same time, since it's been quite easy to retain 1.x/2.7 support so far, this has remained to offer ongoing feature support for older apps that may still be using this. Nonetheless, the plan is now to officially deprecate Django 1.x/Py 2.7 support in django_drf_filepond v0.5.0 and then remove it v0.6.0 - issue #70 is in place to support cleanup when 2.7 support is removed. I'll hold this PR for now and then pull it in when changes for 0.6.0 start getting merged in. |
|
please add support to Django 4.2 and python3.11 as well |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm pretty sure this can be removed when you drop 1.x support, as they gave up on this >2 years ago